Symbolically Parametrized Modules#664
Draft
kimmeljo wants to merge 2 commits into
Draft
Conversation
… that ROHD modules can generate parametrized SV.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description & Motivation
A limitation in the partial adoption path for ROHD is the case where a ROHD module is meant to be instantiated in a larger non-ROHD (ex: SystemVerilog) context and the larger context expects the ROHD module to be parametrizable at its build/synth time (i.e., after ROHD has generated its output representation for that context).
One option is to put the larger context into a generator framework but that can be a non-starter in some cases.
Hence, the goal is to enable ROHD to generate output that can be parametrized by the output context's build/synth flow. In this PR, we focus only on SystemVerilog.
Related Issue(s)
N/A
Testing
Many new unit tests as well as updates to existing unit tests with new test cases as needed.
Backwards-compatibility
The intent is for this to be fully backwards compatible. I.e., this is a new, additive construct.
Documentation
Dedicated documentation provided for this feature.